feat: use uv pip compile for update-constraints
#26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pip-tools are very slow. What takes it 10+ minutes to resolve all dependencies can be done in seconds with `uv`. This is especially problematic when we attempt to run `update-constraints` against a repo with a huge dependency tree (like instructlab/instructlab) which may even time out in gate because of how slow pip-compile is. `uv pip compile` is, largely, a drop-in replacement for `pip-compile`, so the transition is very simple. Signed-off-by: Ihar Hrachyshka <[email protected]>
Contributor
Author
courtneypacheco
approved these changes
May 30, 2025
ktdreyer
approved these changes
May 30, 2025
Contributor
|
@mergify backport release-v0.2 |
Contributor
✅ Backports have been createdDetails
|
5 tasks
mergify bot
added a commit
that referenced
this pull request
May 30, 2025
pip-tools are very slow. What takes it 10+ minutes to resolve all dependencies can be done in seconds with `uv`. This is especially problematic when we attempt to run `update-constraints` against a repo with a huge dependency tree (like instructlab/instructlab) which may even time out in gate because of how slow pip-compile is. `uv pip compile` is, largely, a drop-in replacement for `pip-compile`, so the transition is very simple. Signed-off-by: Ihar Hrachyshka <[email protected]> **Checklist:** - [ ] **Commit Message Formatting**: Commit titles and messages follow guidelines in the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#summary). - [ ] [Changelog](https://github.com/instructlab/ci-actions/blob/main/CHANGELOG.md) updated with breaking and/or notable changes for the next minor release. - [ ] Documentation has been added and/or updated, if applicable. - [ ] Unit tests have been added and/or updated. (If this is not applicable, please provide a justification.) - [ ] Integration testing has been performed, if applicable ## Description of this Change <hr>This is an automatic backport of pull request #26 done by [Mergify](https://mergify.com). Approved-by: courtneypacheco Approved-by: ktdreyer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pip-tools are very slow. What takes it 10+ minutes to resolve all
dependencies can be done in seconds with
uv. This is especiallyproblematic when we attempt to run
update-constraintsagainst a repowith a huge dependency tree (like instructlab/instructlab) which may
even time out in gate because of how slow pip-compile is.
uv pip compileis, largely, a drop-in replacement forpip-compile,so the transition is very simple.
Signed-off-by: Ihar Hrachyshka [email protected]
Checklist:
Description of this Change